Short range digital radio location determination to facilitate petroleum transport

ABSTRACT

A method may include the following steps: determining, based on timing measurements between a first digital radio communication device (DRCD) node and at least a second DRCD node, a distance between the first DRCD disposed on a tanker and the second DRCD disposed about a loading/unloading facility; and facilitating, in response to determining a position based on the timing measurements, fluid payload loading/unloading of the tanker at the loading/unloading facility.

BACKGROUND

One of the problems faced in North American petroleum road tankerloading terminals is contamination and product disposal that are resultsof cross coupling, which is loading product into an incorrectcompartment on a tanker (e.g., truck).

SUMMARY

This summary is provided to introduce a selection of concepts that arefurther described below in the detailed description. This summary is notintended to identify key or essential features of the claimed subjectmatter, nor is it intended to be used as an aid in limiting the scope ofthe claimed subject matter.

In one aspect, the present disclosure may relate to a method which mayinclude the following steps: determining, based on a timing measurementbetween a first digital radio communication device (DRCD) node and asecond DRCD node, a distance between the first DRCD disposed on a tankerand the second DRCD disposed about a loading/unloading facility; andfacilitating, in response to determining the distance based on thetiming measurement, fluid payload loading/unloading of the tanker at theloading/unloading facility.

In another aspect, the present disclosure may relate to a computerprogram product including computer readable program code fordetermining, based on a timing measurement between a first digital radiocommunication device (DRCD) node and a second DRCD node, a distancebetween the first DRCD disposed on a tanker and the second DRCD disposedabout a loading/unloading facility, and facilitating, in response todetermining the distance based on the timing measurement, fluid payloadloading/unloading of the tanker at the loading/unloading facility.

In another aspect, the present disclosure may relate to a distributionsystem which may include one or more computer processors, and a terminalautomation system. The terminal automation system may includeinstructions which, when executed, cause the one or more computerprocessors to determine, based on a timing measurement between a firstdigital radio communication device (DRCD) node and a second DRCD node, adistance between the first DRCD disposed on a tanker and the second DRCDdisposed about a loading/unloading facility; and facilitate, in responseto determining the distance based on the timing measurement, fluidpayload loading/unloading of the tanker at the loading/unloadingfacility.

Other aspects and advantages will be apparent from the followingdescription and the appended claims.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows a system diagram in accordance with one or moreembodiments.

FIG. 2 shows a flowchart in accordance with one or more embodiments.

FIGS. 3, 4, 5, and 6 show an example in accordance with one or moreembodiments.

FIGS. 7.1 and 7.2 show a computing system in accordance with one or moreembodiments.

DETAILED DESCRIPTION

Specific embodiments will now be described in detail with reference tothe accompanying figures. Like elements in the various figures aredenoted by like reference numerals for consistency.

In the following detailed description of embodiments, numerous specificdetails are set forth in order to provide a more thorough understanding.However, it will be apparent to one of ordinary skill in the art thatembodiments may be practiced without these specific details. In otherinstances, well-known features have not been described in detail toavoid unnecessarily complicating the description.

In the following description, any component described with regard to afigure, in various embodiments of the present disclosure, may beequivalent to one or more like-named components described with regard toany other figure. For brevity, at least a portion of these componentsare implicitly identified based on various legends. Further,descriptions of these components will not be repeated with regard toeach figure. Thus, each and every embodiment of the components of eachfigure is incorporated by reference and assumed to be optionally presentwithin every other figure having one or more like-named components.Additionally, in accordance with various embodiments of the presentdisclosure, any description of the components of a figure is to beinterpreted as an optional embodiment which may be implemented inaddition to, in conjunction with, or in place of the embodimentsdescribed with regard to a corresponding like-named component in anyother figure. In the figures, black solid collinear dots indicate thatadditional components similar to the components before and/or after thesolid collinear dots may optionally exist.

Throughout the application, ordinal numbers (e.g., first, second, third,etc.) may be used as an adjective for an element (i.e., any noun in theapplication). The use of ordinal numbers is not to imply or create anyparticular ordering of the elements nor to limit any element to beingonly a single element unless expressly disclosed, such as by the use ofthe terms “before”, “after”, “single”, and other such terminology.Rather, the use of ordinal numbers is to distinguish between theelements. By way of an example, a first element is distinct from asecond element, and the first element may encompass more than oneelement and succeed (or precede) the second element in an ordering ofelements.

In general, example embodiments of the present disclosure provide asystem, a method, and a computer readable medium for facilitatingpetroleum loading/unloading of a tanker at a loading/unloading facility.In one or more embodiments of the present disclosure, digital radiocommunication device (DRCD) nodes are disposed on the tanker andthroughout the loading/unloading facility. The DRCD nodes are configuredto measure distances within a short range. In particular, the distanceis measured based on a timing measurement (e.g., packet-time-of-flight)between the DRCD nodes, such as between a DRCD node mounted on acompartment coupler of the tanker and another DRCD node mounted on aloading/unloading equipment of the loading/unloading facility.Accordingly, petroleum loading/unloading is facilitated in response tomeasuring the distance based on the packet-time-of-flight. For example,a potential cross coupling event may be detected prior to actualoccurrence of the cross coupling to prevent incorrect loading orunloading. Embodiments offer the advantage of low retrofit cost and mayserve other needs at loading terminals such as vehicle identification,vehicle position in the terminal, and data communications with thevehicle (e.g., transferring compartment information such as capacity,Bills of Lading, etc.).

FIG. 1 shows a system (100) in accordance with one or more embodiments.In one or more embodiments, one or more of the modules and elementsshown in FIG. 1 may be omitted, repeated, and/or substituted.Accordingly, embodiments of the present disclosure should not beconsidered limited to the specific arrangements of modules shown in FIG.1.

In one or more embodiments of the present disclosure, the system (100)is based on the short range digital active radiolocation technology toassist in managing activities related to vehicle transport of fluid(e.g., liquid, gas, and/or compressed gas) products. In particular, thesystem (100) includes a collection of devices that achievesidentification, location, relative location, and wireless communicationsto provide assurances during activities such as loading, unloading,vehicle movement, asset movement, custody transfer, and providinginformation to personnel. In one or more embodiments, the system (100)includes a tanker (101) having a cab (101-1) and multiple compartments(e.g., compartment A (101-2), compartment B (101-3), etc.) and aloading/unloading facility (111) having various equipment (e.g.,equipment A (111-1), equipment B (111-2), equipment C (111-3), etc.).Further, one or more DRCD nodes (e.g., DRCD node A (102) having a rangeA (102-1), DRCD node B (112) having a range B (112-1), etc.) aredisposed throughout various locations of the tanker (101) and theloading/unloading facility (111). As shown in FIG. 1, the system (100)is based on the following terminology.

A node may comprise a device containing digital radio communicationstechnology that may have a fixed or mobile location, and may transmitand receiving general information as well as measuring timing (e.g.,used in determination of packet-time-of-flight) information such thatdistance and potentially position (between nodes) may be computed eitheron board or externally. Nodes may contain RF communications device(s)and computer processors, and may or may not contain additionalprocessors, memory, non-volatile memory, sensors (such as but notlimited to accelerometers, magnetometers, gyroscopes), display devices,buttons (or other human input devices), or indicator devices. In certainembodiments, nodes may take on one or more roles in its function,including, but not limited to communication, tag, and anchor (definedbelow).

The term “communication” may refer to a role of a node as configured tosend/receive data packet(s) to/from other nodes. A single node mayperform multiple roles within a communication system. For example, in anexemplary embodiment, a node disposed on a loading arm may function asboth a tag and an anchor. In other embodiments, a note may function aseither a tag or an anchor.

The term “tag” (“tagged”) may refer to a role of a node as being mobilerelative to other nodes.

The term “anchor” may refer to the role of a node as being fixed inlocation or relative to an object to which it is attached. An anchor maybe attached to an object which is fixed or to an object which is mobile.In this way, the anchor may be either fixed or mobile from a globalperspective, and is fixed from a local perspective. In a first exemplaryembodiment, an anchor may be fixed to a stationary object, such as apiece of equipment at a terminal. The anchor may be fixed both relativeto the piece of equipment and relative to a global perspective. In asecond exemplary embodiment, an anchor may be fixed to a mobile object,such as a tanker or a loading arm. The anchor may be fixed relative tothe tanker or the loading arm and mobile from a global perspective.

A tanker may comprise a vehicle used to transport fluid payload, such asliquids, liquefied gases, gases, compressed gasses, or refrigeratedliquefied gases; including but not limited to road vehicles,boats/ships, aircraft, space vehicles (rockets), and rail cars. “Tanker”may also refer to the vehicle itself, for example, when undergoingfueling and other provisioning operations. Also, may be a servicevehicle that is equipped with node(s), such as a meter prover truck (mayor may not contain a storage tank).

A terminal may comprise a facility where tankers may be loaded and/orunloaded. Metering of product and/or custody transfer may or may nottake place.

Recent developments in short range wireless digital communicationstechnology allow for measurement of timing and deriving packettime-of-flight (reference IEEE802.15.4-2011) in a low cost economicpackage; this functionality allows for determination of distance betweennodes and, with suitable geometry, relative position with resolution notavailable before in commonly available components. Current technologyallows distance and position measurement with a resolution of about ±10cm (±4 in) (reference “DecaWave”, http://www.decawave.com/); thisability may be applied to tanker and terminal applications to achieve asynergistic mix of capabilities at a low-price point not achievable withother technologies.

One or more embodiments of the present disclosure provide operationalassurances and features by affixing short range radiolocation technology(i.e., nodes) to fixed terminal facilities, mobile terminal equipment,tankers, tanker equipment (e.g., hose ends), and to other equipment suchas computers, user interfaces, and network gateways, as described below.

Certain embodiments provide the functionality of controlling access(hereinafter “feature 1”). Tagged mobile asset (such as tankers)position may be wirelessly identified and identity authenticated forentry or exit from a terminal yard or other secure areas that requirerestricted access.

Certain embodiments provide the functionality of preventing loadingproduct to the wrong tanker (hereinafter “feature 2”). Tagged load armposition relative to a tagged tanker may be used to determine if the armis delivering to the correct tanker.

Certain embodiments provide the functionality of product cross-over(mixing) prevention (hereinafter “feature 3”). Tagged load arm relativeposition to a tagged tanker may be used to determine if the arm isdelivering to the correct compartment coupling on a Tanker.

Certain embodiments provide the functionality of yard operations, suchas queuing tankers (hereinafter “feature 4”). Position of tagged tankersin the terminal yard, including direction of travel (even whenmotionless), may be used to compute optimum queuing of loading stations,unloading stations, waiting areas, and other activities.

Certain embodiments provide the functionality of mobile asset collisionwarnings (hereinafter “feature 5”). Tagged mobile assets and taggedfixed assets relative positions may be computed and monitored to warnagainst hazardous situations; for example, a load arm is not retractedfrom a tanker.

Certain embodiments provide the functionality of product cross-over(mixing) prevention at drop locations (e.g., gas station) where tankersunload (hereinafter “feature 6”). Tanker anchors position the couplersand identify products available at each coupler, terminal area anchorsposition the tank filler locations and identify the product that isacceptable, and tagged hose ends determine which coupler is feedingwhich tank filler. A communicating device may then optionally display ago/no go indication to the operator and log information.

Certain embodiments provide the functionality of transferring tankerconfiguration information from the tanker to the terminal (hereinafter“feature 7”). Tanker configuration information may includeidentification, compartment count, compartment capacities, compartmentcoupler positions relative to the tanker anchors.

Certain embodiments provide the functionality of transferring tankerstatus to the terminal (hereinafter “feature 8”). Tanker status mayinclude connected sensor information like compartment fluid levels,point level sensors (compartment empty/full status), last product loadedin each compartment (e.g., recalled from on-board memory written duringthe last load), tanker location history (e.g., gps log), product drop(e.g., unloading) logs, and other business related information that maybe stored on board the Tanker.

Certain embodiments provide the functionality of information storage onthe tagged tanker (hereinafter “feature 9”). The terminal automationsystem may store information in the node tagged on the tanker forpurposes of identification or saving state information, similar to howweb servers save “cookies” on a user's computer.

Certain embodiments provide the functionality of transferringinformation from terminal automation systems to the tanker and/or cabmounted devices such as Bills of Lading, product type just loaded intocompartments, delivery locations and routing, driver instructions, andbusiness information relating to the transaction or vehicle load(hereinafter “feature 10”).

Certain embodiments provide the functionality of wireless communicationsto facilitate installation, configuration, and calibration of nodes,possibly using relative position information during the process(hereinafter “feature 11”).

Certain embodiments provide the functionality of wirelesscommunications, between proving trucks and terminal facilities, forproving the calibration of fluid metering equipment (hereinafter“feature 12”). For example, information such as the identity of theproving vehicle, which load arm is being used to flow product to theprover (ultimately which meter is being tested), and new meter factors(calibrations factors) may be communicated back to the terminalfacility.

Certain embodiments provide the functionality of generating a map of theloading/unloading facility based at least on the distance between atagged tanker and anchors disposed about the terminal yard (hereinafter“feature 13”). For example, the map may be displayed on a cab-mounteddevice of the tanker or a terminal automation system of theloading/unloading facility.

FIG. 2 shows a method flowchart in accordance with one or moreembodiments. One or more blocks shown in FIG. 2 may be omitted,repeated, and/or performed in a different order among differentembodiments. Accordingly, embodiments should not be considered limitedto the specific number and arrangement of blocks shown in FIG. 2.

Initially, in Block 211, a first digital radio communication device(DRCD) node is disposed on a tanker to identify at least a compartmentcoupler of the tanker. For example, the first DRCD node may be mounteddirectly on the compartment coupler. In another example, the first DRCDmay be mounted on a position with fixed geometry relative to thecompartment coupler.

In Block 212, a second DRCD node is disposed about a loading/unloadingfacility to identify at least a loading/unloading equipment of theloading/unloading facility. For example, the second DRCD node may bedisposed on a loading arm or a hose end of the loading/unloadingfacility. In another example, the second DRCD may be mounted on aposition with fixed geometry relative to the loading arm or the hoseend.

In Block 213, a distance between the compartment coupler and theloading/unloading equipment is determined based on a timing measurement(e.g., packet-time-of-flight) between the first DRCD node and the secondDRCD node. In one or more embodiments, a data packet is sent from thefirst DRCD node to the second DRCD node. The packet may include atransmitting timestamp inserted by the first DRCD node to represent thetime when the packet is sent from the first DRCD node. The second DRCDnode may record a receiving timestamp to represent the time when thepacket is received at the second DRCD node. Accordingly, the timingmeasurement (e.g., packet-time-of-flight) may be derived based on thetransmitting timestamp and the receiving timestamp. For example, thetiming measurement (e.g., packet-time-of-flight) may include adifference between the transmitting timestamp and the receivingtimestamp. In one or more embodiments, deriving the timing measurement(e.g., packet-time-of-flight) may include a multi-step process involvingback and forth communications between the first DRCD node and the secondDRCD node. Based on the timing measurement (e.g.,packet-time-of-flight), the distance may then be determined bymultiplying the timing measurement and a pre-determined factor. Forexample, the pre-determined factor may correspond to a transmissionspeed of the data packet between the first DRCD node and the second DRCDnode.

In Block 214, in response to determining the distance based on thetiming measurement (e.g., packet-time-of-flight) between the first DRCDnode and the second DRCD node, fluid payload loading/unloading of thetanker at the loading/unloading facility is facilitated. In one or moreembodiments, the fluid payload includes petroleum or other liquefiedgas. In one or more embodiments, a potential error condition is detectedbased on the measured distance. Accordingly, the loading/unloading ofthe tanker is adjusted or otherwise facilitated based on the detectederror condition. Various example embodiments of detecting the errorcondition and facilitating the loading/unloading of the tanker aredescribed in details below.

In one or more embodiments, facilitating loading/unloading of the tankerincludes wirelessly identifying tagged mobile asset (such as tankers)position authenticating identity for entry or exit from a terminal yardor other secure areas that require restricted access.

In one or more embodiments, facilitating loading/unloading of the tankerincludes preventing loading product to the wrong tanker. For example,tagged load arm position relative to a tagged tanker may be used todetermine if the arm is delivering to the correct tanker.

In one or more embodiments, facilitating loading/unloading of the tankerincludes preventing product cross-over (mixing) while at the loadingfacility. For example, tagged load arm relative position to a taggedtanker may be used to determine if the arm is delivering to the correctcompartment coupling on a Tanker.

In one or more embodiments, facilitating loading/unloading of the tankerincludes facilitating yard operations, such as queuing tankers. Forexample, position of tagged tankers in the terminal yard, includingdirection of travel (even when motionless), may be used to computeoptimum queuing of loading stations, unloading stations, waiting areas,and other activities.

In one or more embodiments, facilitating loading/unloading of the tankerat the loading/unloading facility includes providing mobile assetcollision warnings. For example, tagged mobile assets and tagged fixedassets relative positions may be computed and monitored to warn againsthazardous situations; for example, a load arm is not retracted from atanker.

In one or more embodiments, facilitating loading/unloading of the tankerincludes preventing product cross-over (mixing) at drop locations (e.g.,gas station) where tankers unload. For example, tanker anchors positionthe couplers and identify products available at each coupler,terminal/fuel station area anchors (one or several, which can beinstalled in/on fixed or mobile/portable/hand held devices) position thetank filler locations and identify the product that is acceptable, andtagged hose ends determine which coupler is feeding which tank filler.Alternative to tagged hose ends: portable/mobile/hand held device whichidentifies automatically or with the help of an operator, andcommunicates, the position of each hose end. A communicating device maythen optionally display a go/no go indication to the operator or hindersthe delivery (e.g. does not release the compressed air) and loginformation.

In one or more embodiments, facilitating loading/unloading of the tankerincludes transferring tanker configuration information from the tankerto the terminal. For example, tanker configuration information mayinclude identification, compartment count, compartment capacities, orcompartment coupler positions relative to the tanker anchors.

In one or more embodiments, facilitating loading/unloading of the tankerincludes transferring tanker status to the terminal. For example, tankerstatus may include connected sensor information like compartment fluidlevels, point level sensors (compartment empty/full status), lastproduct loaded in each compartment (e.g., recalled from on-board memorywritten during the last load), tanker location history (e.g., gps log),product drop (e.g., unloading) logs, and other business relatedinformation that may be stored on board the Tanker.

In one or more embodiments, facilitating loading/unloading of the tankerincludes providing information storage on the tagged tanker. Forexample, the terminal automation system may store information in thenode tagged on the tanker for purposes of identification or saving stateinformation, similar to how web servers save “cookies” on a user'scomputer.

In one or more embodiments, facilitating loading/unloading of the tankerincludes transferring information from terminal automation systems tothe tanker and/or cab mounted devices such as Bills of Lading, producttype just loaded into compartments, delivery locations and routing,driver instructions, and business information relating to thetransaction or vehicle load.

In one or more embodiments, facilitating loading/unloading of the tankerincludes using wireless communications to facilitate installation,configuration, and calibration of nodes, possibly using relativeposition information during the process.

In one or more embodiments, facilitating loading/unloading of the tankerincludes generating a map of the loading/unloading facility based atleast on the distance between a tagged tanker and anchors disposed aboutthe terminal yard. For example, the map may be displayed on acab-mounted device of the tanker or a terminal automation system of theloading/unloading facility.

Additional examples of facilitating petroleum loading/unloading of thetanker are described in reference to FIGS. 3, 4, 5, and 6 below.

FIGS. 3, 4, 5, and 6 show an example in accordance with one or moreembodiments. In one or more embodiments, one or more of the modules andelements shown in FIGS. 3, 4, 5, and 6 may be omitted, repeated, and/orsubstituted. Accordingly, embodiments of the present disclosure shouldnot be considered limited to the specific arrangements of modules shownin FIGS. 3, 4, 5, and 6.

In particular, FIGS. 3 and 4 show examples of cross coupling preventionin a side-loading scenario and top-loading scenario, respectively. Asshown in FIGS. 3 and 4, anchor nodes are mounted to the tanker inpositions marked “A”, tag nodes are mounted to each of the loading armsin positions marked “T”, and a communications node mounted elsewhere(represented by a position marked “C”) that is connected to acommunications network, which is part of the terminal. In theside-loading scenario depicted in FIG. 3, a bottom loading tanker isshown where the couplers are on the side.

During the process of mounting and commissioning the anchor nodes, theirmounting geometry relative to the compartment couplers on the tanker aredetermined and stored in the system. For example, the information may bestored in a non-volatile memory device imbedded in the anchor nodes. Asan alternative, the geometry may be pre-specified and the mountingpositions restricted to specific locations relative to the couplers.

During the process of mounting and commissioning the tag nodes, theirmounting geometry relative to the load arm are determined and stored inthe system. For example, the information may be stored in a non-volatilememory device imbedded in the tag nodes. As an alternative, the geometrymay be pre-specified and the mounting positions restricted to specificlocations relative to the load arms.

The tags on the load arms broadcast a unique identification code and thestored geometry. The broadcast may be periodic or triggered by a sensorthat detects arm activity. The unique identification code is utilized todifferentiate the broadcasts such that the identity of the arm may bedetermined.

The anchor nodes receive the tag broadcasts to compute possiblepositions of the load arm relative to the tanker couplings based on thereceived arm identification code, the tag geometry with respect to thearm, identification codes stored in the anchors, and message timinginformation. The received broadcasted information and/or the computedpositions are then transmitted.

The communications node connected with other systems at the terminalreceives the information transmitted from the anchors, and forwards theinformation to systems that may then use that information to ensure thatthe load arm is connected to the correct tanker (e.g., using the anchoridentification codes), and to the correct compartment coupler using therelative position computations.

As the nodes are part of a wireless network, the system is flexible asto where the computations take place to achieve the purpose. Forexample, the tag and anchor nodes may simply forward the basicinformation cited above, and the computations performed on a computerthat is part of the terminal system.

FIGS. 5 and 6 show additional examples of loading/unloading facilityoperations in accordance with one or more embodiments. In particular,FIG. 5 shows a schematic layout diagram of a road tanker loading yard.FIG. 6 shows a schematic layout diagram of a gas station (drop point).

Consider a road tanker equipped with anchor nodes (e.g., as shown inFIGS. 3 and 4) as well as a communications node equipped user interface(e.g., with a printer) in the truck cab. This cab mounted system alsocontains a GPS and memory. The tanker is also equipped with levelsensing devices in the compartments that interfaced with the wirelessnodes that communicate with either (or both) the cab unit and terminalyard systems. Note that functionality described below assumes thisconfiguration, but there is flexibility in where the devices may bemounted. For example, the GPS may be connected to the tanker nodes,rather than the cab device. Finally, the tanker is equipped with anunloading hose, which has a tag node affixed to each end, and thesenodes have been previously configured to identify each other as beingattached to the same hose.

Further, consider a loading yard (as shown in FIG. 5) equipped with atag node on each loading arm (located in “bays”), and other anchor nodes(denoted as “A” within a circle) located around the facility with aknown geometry useful for computing location information from timingmeasurements (e.g., measured packet-time-of-flight, derived fromdifferential timing of multiple packets, etc.). The loading yard isequipped with an entrance gate, a staging area, the loading bays, and anexit gate.

Finally, consider a gas station (as shown in FIG. 6) that has anchornodes (one or several) positioned such that the gas station tankcoupling positions on the ground are mapped and the configuration storedin memory contained in the nodes. This may include the possibility thatthese nodes are located in the lids of the gas station receptacles, orin one or several fixed or mobile/portable/hand held devices, placed atthe locations marked A in a circle on FIG. 6 or at other locations atthe fuel station.

As the tanker approaches the entrance gate, the fixed nodes in the yardcommunicate with the nodes affixed to the tanker as they come intocommunications range and forward identification (e.g., based on feature7) and tanker position (e.g., based on feature 4) (e.g., derived frompacket-time-of-flight) information to the terminal computer system. Theterminal system determines by position that the tanker is first in lineof potentially more tankers ready to enter the gate, and by databaselookup using the identification, that it is authorized to access thefacility; the gate is then opened to permit access (e.g., based onfeature 1). The cab mounted node also transmits to the terminal system aGPS log (e.g., based on feature 10) and level sensor log which arestored (e.g., based on feature 8) and may be used to determine, forexample, that the previous load was dropped (unloaded) at specific GPScoordinates. Further, the operator in the tanker cab desires to load1500 gallons of gasoline and 500 gallons of diesel, and has entered thisinto the user interface located in the cab. The radio node in the cabtransmits this “fuel order” information to the terminal system (e.g.,based on feature 10), and the terminal uses the position information ofthe cab node related to the position information from the tanker(trailer) nodes to determine that this operator is hauling the specifiedtanker trailer (trucker in cab is identified with the tanker asset)(e.g., based on feature 4). The terminal system examines the fuel ordertransmitted by the trucker, and determines that a loading bay forgasoline is available, and sends a message to the cab user interfacedirecting the trucker to that specific bay (e.g., based on feature 4).

The trucker proceeds to that bay, and couples the gasoline arm to atanker compartment. The terminal system determines that the loading armis connected to the correct tanker using the identity and position ofthe tanker relative to the arm (e.g., based on feature 2). Further,using the cross-coupling features described above, the terminal systemdetermines that the gasoline arm is coupled to a compartment last usedfor diesel (e.g., based on feature 3) (the compartment last useinformation may come from information stored in the tanker nodes writtenduring the last load, or from a database that is part of the terminalsystem that has the last load and tanker/compartment recorded). Theterminal system does not allow delivery to start because it would causea cross contamination condition, and the trucker is then informed thatthe coupling is incorrect. After the trucker changes the loading arm tothe correct compartment, the level sensor information (live readings)and the compartment capacity (stored during configuration) for thecompartment to which the arm is connected is requested and transmittedto the terminal system (e.g., based on features 7 and 8), whichdetermines that the compartment still has a partial load aboard (thelevel is not “empty”). The Terminal system then discloses this to thetrucker through a user interface, who then opts to reduce his ordervolume. The terminal system affirms that there is enough remainingcapacity aboard the tanker to accept the requested order, and permitsloading to take place. Once the gasoline order is loaded, the terminalsystem transmits the product type loaded to the tanker, where thatinformation is stored on board for future use (e.g., based on feature9). The trucker disconnects the arm and returns to the cab, where thecab user interface display instructs the trucker to report to a stagingarea because no diesel loading arms are available at that time (e.g.,based on feature 4).

While waiting in the staging area, the terminal detects the diesel bayis free (using position information from the Tanker previously occupyingthat bay) (e.g., based on feature 4), but also determines the tanker inthe staging area is behind another (by using position information)(e.g., based on feature 4), and sends a message to the cab of the othertrucker (in front) that he is next to load (e.g., based on feature 10).

Suppose the terminal has two diesel loading bays; the terminal senses(by position) that one of these bays is occupied by a proving truck(also equipped with a node) (e.g., based on feature 7). Further, theloading arm connected to the prover truck transmits its identity, andthe node on the prover truck determined the arm identity to which it iscoupled (e.g., based on feature 2); this information is wirelesslyforwarded to the terminal system, which uses the arm identity to look upwhich meter is on that line (the meter being proved), and forwards themeter identity back to the prover truck. Thus, the meter being proven isautomatically identified to the system aboard the prover truck. Afterproving runs are done, the new meter factors are forwarded back to theterminal system (e.g., based on feature 8) which then records theactivity and sets the new meter factors (calibration) into the meter.

While this is taking place, the other diesel bay is cleared, and theexample trucker waiting in the staging area is instructed to report tothe open diesel bay using the wireless protocol and the cab userinterface (e.g., based on feature 10); however, the trucker pulls intothe wrong bay. The terminal system, using position information derivedfrom the tanker nodes and the fixed terminal nodes (e.g., based onfeature 4), notifies the trucker of the error via the cab user interface(e.g., based on feature 10), and the trucker moves to the correct bay.The trucker loads diesel without further issue.

When the trucker attempts to pull clear of the bay, he sees a red lightindicating he should not move his Tanker; this light is controlled bythe terminal system, which has used the measured distance between theloading arm and the tanker to determine that there is a hazard present(e.g., based on feature 5) (the tagged load arm is still coupled to thetanker, for example). The trucker then examines the situation and findsthat the load arm has been uncoupled, but has not been retracted farenough away from the tanker and still presents a hazard. Afterretracting all the load arms away from the tanker, he is then signaled agreen light and pulls clear of the bay. The nodes in the yard detect (byposition) that the truck is clear of the bay (e.g., based on feature 4),and instructs the next trucker waiting that the bay is now available(e.g., based on features 4 and 10).

The trucker then makes his way to the exit gate, and while doing so, theterminal system transmits the Bill of Lading to the cab user interface(e.g., based on feature 10), which prints it on the connected printer.While pausing at the exit gate, the trucker “signs” the Bill of Ladingusing the user interface, and the signature is transmitted back to theterminal system, which then authorizes exit and opens the exit gate(e.g., based on feature 1).

With reference to FIG. 6, the trucker proceeds to the gas station wherethe load will be deposited; the GPS may log the route taken. The truckerconnects the discharge hose, for example, to the diesel compartment onthe tanker and the other end of the hose to, for example, a gasolinetank at the gas station (an incorrect coupling). The cab unit (or aseparate node equipped unit mounted on the tanker) is communicating withthe anchor nodes on the tanker (denoted as “B” in a circle) and the tagnode on the hose end (denoted as “T”) and uses relative position todetermine that one end of the hose is connected to the dieselcompartment on the Tanker (e.g., based on feature 2). Further, the sameunit communicates with the anchor node or nodes at the gas station(installed in/on one or several fixed or mobile/portable/hand helddevices, placed at the locations marked A in a circle on FIG. 6 or atother locations at the fuel station), and the tag node at the other endof the hose to determine, by relative positions, that it is connected tothe gasoline tank at the station. In some embodiments, aportable/mobile/hand held device which identifies automatically or withthe help of an operator, and communicates, the position of each hoseend, may be used as an alternative to, or in addition to, tagged hoseends.

Finally, the unit identifies the hose end tag nodes as belonging to thesame hose, so it can determine the hose is coupling the dieselcompartment to a gasoline tank (e.g., based on feature 6), and thensignals the trucker visually and/or audibly that the connection isincorrect. Further, if the tanker is so equipped, the unit could preventopening the valve or running a pump so as to avoid discharging the load.The trucker then moves the hose to the station diesel tank, and usingthe same process, the unit may determine the connection is correct, andsignal “okay” to the trucker and allow the valve to be opened. The unitalso may record the tanker compartment level drop using the levelsensor, along with the GPS location information into internal memory tobe transferred upon return to the loading terminal yard (e.g., based onfeature 8). The trucker finishes discharging the tanker contents, andreturns to the terminal for another load.

An addition to the service station drop scenario may include the servicestation anchors interfacing with sensors and transmitting additionaldata, such as level sensors mounted in the service station tanks. Thisdata may be used to prevent starting a drop into a tank without enoughremaining capacity (overfill prevention), and storing and/or forwardingthe tank level data to a business system to determine, for example, whento buy more and in what quantity. The service station anchors may beconfigured with and transmit information to the truck including tankcapacities.

Loading/unloading facility operations in accordance with one or moreembodiments may also include hybrid operations. An operation may includeelements described above, especially with respect to FIGS. 5-6, and mayalso include other types of tracking means.

In some embodiments, different tracking means may be used at differentpoints in the operation. For example, barcodes, RFID tags,ultra-wideband tags, GPS trackers, and/or other types of trackers may beused to identify elements of the system described above at differentstages of the operation. In some embodiments, two or more types oftracking means may be used. In some cases, a hybrid system may havereduced costs and/or complexity compared to a non-hybrid system, mayallow tracking means which are already installed on equipment to be usedin conjunction with the tracking system described above, and may allowdifferent types of tracking systems to be merged easily.

In an exemplary embodiment, tracking within a terminal may be performedusing nodes as described above. Nodes may be attached to both a tankerand to loading equipment at the terminal to facilitate loading of thetanker within the terminal. Nodes may also facilitate movement of thetanker within the terminal, for example from the entrance of theterminal, to the loading site, and to the exit. Tracking outside of theterminal may be performed using a different tracking means. For example,barcodes, RFID tags, ultra-wideband tags, or GPS trackers may be used totrack the movement and operations of the tanker outside of the terminal.The second type of tracking means may be attached to the tanker inaddition to the nodes described above. In some cases, the second type oftracking means may be disposed at a service station drop, or a servicestation drop may include a reader which works in conjunction with thesecond type of tracking means, for example a barcode scanner.

Although an exemplary case is described above, one skilled in the artwill readily recognize that different types of tracking means may becombined within the system in many different ways. For example, nodes asdescribed above may be used outside of a terminal while a differenttracking means is used within the terminal. For another example,different service station drops may use different types of trackingmeans. All necessary types of tracking means may be attached to a tankerto be read at the different service station drops. Further, any type oftracking means known in the art may be used, in addition to thosedescribed explicitly herein.

Embodiments may be implemented on a computing system. Any combination ofmobile, desktop, server, router, switch, embedded device, or other typesof hardware may be used. For example, as shown in FIG. 7.1, thecomputing system (700) may include one or more computer processors(702), non-persistent storage (704) (e.g., volatile memory, such asrandom access memory (RAM), cache memory), persistent storage (706)(e.g., a hard disk, an optical drive such as a compact disk (CD) driveor digital versatile disk (DVD) drive, a flash memory, etc.), acommunication interface (712) (e.g., Bluetooth interface, infraredinterface, network interface, optical interface, etc.), and numerousother elements and functionalities. In one or more embodiments, variousfeatures (e.g., one or more of the feature 1 through feature 13) of thesystem (100) depicted in FIG. 1 above are implemented using at least thecomputing system (700). In one or more embodiments, the method flowchartdepicted in FIG. 2 above is performed using at least the computingsystem (700).

The computer processor(s) (702) may be an integrated circuit forprocessing instructions. For example, the computer processor(s) may beone or more cores or micro-cores of a processor. The computing system(700) may also include one or more input devices (710), such as atouchscreen, keyboard, mouse, microphone, touchpad, electronic pen, orany other type of input device.

The communication interface (712) may include an integrated circuit forconnecting the computing system (700) to a network (not shown) (e.g., alocal area network (LAN), a wide area network (WAN) such as theInternet, mobile network, or any other type of network) and/or toanother device, such as another computing device.

Further, the computing system (700) may include one or more outputdevices (708), such as a screen (e.g., a fluid crystal display (LCD), aplasma display, touchscreen, cathode ray tube (CRT) monitor, projector,or other display device), a printer, external storage, or any otheroutput device. One or more of the output devices may be the same ordifferent from the input device(s). The input and output device(s) maybe locally or remotely connected to the computer processor(s) (702),non-persistent storage (704), and persistent storage (706). Manydifferent types of computing systems exist, and the aforementioned inputand output device(s) may take other forms.

Software instructions in the form of computer readable program code toperform embodiments may be stored, in whole or in part, temporarily orpermanently, on a non-transitory computer readable medium such as a CD,DVD, storage device, a diskette, a tape, flash memory, physical memory,or any other computer readable storage medium. Specifically, thesoftware instructions may correspond to computer readable program codethat, when executed by a processor(s), is configured to perform one ormore embodiments. In one or more embodiments, various features (e.g.,one or more of the feature 1 through feature 11) of the system (100)depicted in FIG. 1 above are implemented using at least aloading/unloading manager, which is a software application having acollection of computer readable program codes. In one or moreembodiments, the method flowchart depicted in FIG. 2 above is performedusing at least the loading/unloading manager.

The computing system (700) in FIG. 7.1 may be connected to or be a partof a network. For example, as shown in FIG. 7.2, the network (720) mayinclude multiple computing nodes (e.g., computing node X (722),computing node Y (724)). Each computing node may correspond to acomputing system, such as the computing system shown in FIG. 7.1, or agroup of computing nodes combined may correspond to the computing systemshown in FIG. 7.1. The computing nodes depicted in FIG. 7.2 are distinctfrom the DRCD nodes described above. By way of an example, embodimentsmay be implemented on a computing node of a distributed system that isconnected to other computing nodes. By way of another example,embodiments may be implemented on a distributed computing system havingmultiple computing nodes, where each portion may be located on adifferent computing node within the distributed computing system.Further, one or more elements of the aforementioned computing system(700) may be located at a remote location and connected to the otherelements over a network.

Although not shown in FIG. 7.2, the computing node may correspond to ablade in a server chassis that is connected to other computing nodes viaa backplane. By way of another example, the computing node maycorrespond to a server in a data center. By way of another example, thecomputing node may correspond to a computer processor or micro-core of acomputer processor with shared memory and/or resources.

The computing nodes (e.g., computing node X (722), computing node Y(724)) in the network (720) may be configured to provide services for aclient device (726). For example, the computing nodes may be part of acloud computing system. The computing nodes may include functionality toreceive requests from the client device (726) and transmit responses tothe client device (726). The client device (726) may be a computingsystem, such as the computing system shown in FIG. 7.1. Further, theclient device (726) may include and/or perform at least a portion of oneor more embodiments.

The computing system or group of computing systems described in FIGS.7.1 and 7.2 may include functionality to perform a variety of operationsdisclosed herein. For example, the computing system(s) may performcommunication between processes on the same or different system. Avariety of mechanisms, employing some form of active or passivecommunication, may facilitate the exchange of data between processes onthe same device. Examples representative of these inter-processcommunications include, but are not limited to, the implementation of afile, a signal, a socket, a message queue, a pipeline, a semaphore,shared memory, message passing, and a memory-mapped file. Furtherdetails pertaining to a couple of these non-limiting examples areprovided below.

Based on the client-server networking model, sockets may serve asinterfaces or communication channel end-points enabling bidirectionaldata transfer between processes on the same device. Foremost, followingthe client-server networking model, a server process (e.g., a processthat provides data) may create a first socket object. Next, the serverprocess binds the first socket object, thereby associating the firstsocket object with a unique name and/or address. After creating andbinding the first socket object, the server process then waits andlistens for incoming connection requests from one or more clientprocesses (e.g., processes that seek data). At this point, when a clientprocess wishes to obtain data from a server process, the client processstarts by creating a second socket object. The client process thenproceeds to generate a connection request that includes at least thesecond socket object and the unique name and/or address associated withthe first socket object. The client process then transmits theconnection request to the server process. Depending on availability, theserver process may accept the connection request, establishing acommunication channel with the client process, or the server process,busy in handling other operations, may queue the connection request in abuffer until server process is ready. An established connection informsthe client process that communications may commence. In response, theclient process may generate a data request specifying the data that theclient process wishes to obtain. The data request is subsequentlytransmitted to the server process. Upon receiving the data request, theserver process analyzes the request and gathers the requested data.Finally, the server process then generates a reply including at leastthe requested data and transmits the reply to the client process. Thedata may be transferred, more commonly, as datagrams or a stream ofcharacters (e.g., bytes).

Shared memory refers to the allocation of virtual memory space in orderto substantiate a mechanism for which data may be communicated and/oraccessed by multiple processes. In implementing shared memory, aninitializing process first creates a shareable segment in persistent ornon-persistent storage. Post creation, the initializing process thenmounts the shareable segment, subsequently mapping the shareable segmentinto the address space associated with the initializing process.Following the mounting, the initializing process proceeds to identifyand grant access permission to one or more authorized processes that mayalso write and read data to and from the shareable segment. Changes madeto the data in the shareable segment by one process may immediatelyaffect other processes, which are also linked to the shareable segment.Further, when one of the authorized processes accesses the shareablesegment, the shareable segment maps to the address space of thatauthorized process. Often, one authorized process may mount theshareable segment, other than the initializing process, at any giventime.

Other techniques may be used to share data, such as the various datadescribed in the present application, between processes withoutdeparting from the scope. The processes may be part of the same ordifferent application and may execute on the same or different computingsystem.

Rather than or in addition to sharing data between processes, thecomputing system performing one or more embodiments may includefunctionality to receive data from a user. For example, in one or moreembodiments, a user may submit data via a graphical user interface (GUI)on the user device. Data may be submitted via the graphical userinterface by a user selecting one or more graphical user interfacewidgets or inserting text and other data into graphical user interfacewidgets using a touchpad, a keyboard, a mouse, or any other inputdevice. In response to selecting a particular item, informationregarding the particular item may be obtained from persistent ornon-persistent storage by the computer processor. Upon selection of theitem by the user, the contents of the obtained data regarding theparticular item may be displayed on the user device in response to theuser's selection.

By way of another example, a request to obtain data regarding theparticular item may be sent to a server operatively connected to theuser device through a network. For example, the user may select auniform resource locator (URL) link within a web client of the userdevice, thereby initiating a Hypertext Transfer Protocol (HTTP) or otherprotocol request being sent to the network host associated with the URL.In response to the request, the server may extract the data regardingthe particular selected item and send the data to the device thatinitiated the request. Once the user device has received the dataregarding the particular item, the contents of the received dataregarding the particular item may be displayed on the user device inresponse to the user's selection. Further to the above example, the datareceived from the server after selecting the URL link may provide a webpage in Hyper Text Markup Language (HTML) that may be rendered by theweb client and displayed on the user device.

Once data is obtained, such as by using techniques described above orfrom storage, the computing system, in performing one or moreembodiments, may extract one or more data items from the obtained data.For example, the extraction may be performed as follows by the computingsystem in FIG. 7.1. First, the organizing pattern (e.g., grammar,schema, layout) of the data is determined, which may be based on one ormore of the following: position (e.g., bit or column position, Nth tokenin a data stream, etc.), attribute (where the attribute is associatedwith one or more values), or a hierarchical/tree structure (consistingof layers of computing nodes at different levels of detail—such as innested packet headers or nested document sections). Then, the raw,unprocessed stream of data symbols is parsed, in the context of theorganizing pattern, into a stream (or layered structure) of tokens(where each token may have an associated token “type”).

Next, extraction criteria are used to extract one or more data itemsfrom the token stream or structure, where the extraction criteria areprocessed according to the organizing pattern to extract one or moretokens. For position-based data, the token(s) at the position(s)identified by the extraction criteria are extracted. Forattribute/value-based data, the token(s) associated with theattribute(s) satisfying the extraction criteria are extracted. Forhierarchical/layered data, the token(s) matching the extraction criteriaare extracted. The extraction criteria may be as simple as an identifierstring or may be a query presented to a structured data repository(where the data repository may be organized according to a databaseschema or data format, such as XML).

The extracted data may be used for further processing by the computingsystem. For example, the computing system of FIG. 7.1, while performingone or more embodiments, may perform data comparison. Data comparisonmay be used to compare two or more data values (e.g., A, B). Forexample, one or more embodiments may determine whether A>B, A=B, A !=B,A<B, etc. The comparison may be performed by submitting A, B, and anopcode specifying an operation related to the comparison into anarithmetic logic unit (ALU) (i.e., circuitry that performs arithmeticand/or bitwise logical operations on the two data values). The ALUoutputs the numerical result of the operation and/or one or more statusflags related to the numerical result. For example, the status flags mayindicate whether the numerical result is a positive number, a negativenumber, zero, etc. By selecting the proper opcode and then reading thenumerical results and/or status flags, the comparison may be executed.For example, in order to determine if A>B, B may be subtracted from A(i.e., A−B), and the status flags may be read to determine if the resultis positive (i.e., if A>B, then A−B>0). In one or more embodiments, Bmay be considered a threshold, and A is deemed to satisfy the thresholdif A=B or if A>B, as determined using the ALU. In one or moreembodiments, A and B may be vectors, and comparing A with B involvescomparing the first element of vector A with the first element of vectorB, the second element of vector A with the second element of vector B,etc. In one or more embodiments, if A and B are strings, the binaryvalues of the strings may be compared.

The computing system in FIG. 7.1 may implement and/or be connected to adata repository. For example, one type of data repository is a database.A database is a collection of information configured for ease of dataretrieval, modification, re-organization, and deletion. DatabaseManagement System (DBMS) is a software application that provides aninterface for users to define, create, query, update, or administerdatabases.

The user, or software application, may submit a statement or query intothe DBMS. Then the DBMS interprets the statement. The statement may be aselect statement to request information, update statement, createstatement, delete statement, etc. Moreover, the statement may includeparameters that specify data, or data container (database, table,record, column, view, etc.), identifier(s), conditions (comparisonoperators), functions (e.g. join, full join, count, average, etc.), sort(e.g. ascending, descending), or others. The DBMS may execute thestatement. For example, the DBMS may access a memory buffer, a referenceor index a file for read, write, deletion, or any combination thereof,for responding to the statement. The DBMS may load the data frompersistent or non-persistent storage and perform computations to respondto the query. The DBMS may return the result(s) to the user or softwareapplication.

The computing system of FIG. 7.1 may include functionality to presentraw and/or processed data, such as results of comparisons and otherprocessing. For example, presenting data may be accomplished throughvarious presenting methods. Specifically, data may be presented througha user interface provided by a computing device. The user interface mayinclude a GUI that displays information on a display device, such as acomputer monitor or a touchscreen on a handheld computer device. The GUImay include various GUI widgets that organize what data is shown as wellas how data is presented to a user. Furthermore, the GUI may presentdata directly to the user, e.g., data presented as actual data valuesthrough text, or rendered by the computing device into a visualrepresentation of the data, such as through visualizing a data model.

For example, a GUI may first obtain a notification from a softwareapplication requesting that a particular data object be presented withinthe GUI. Next, the GUI may determine a data object type associated withthe particular data object, e.g., by obtaining data from a dataattribute within the data object that identifies the data object type.Then, the GUI may determine any rules designated for displaying thatdata object type, e.g., rules specified by a software framework for adata object class or according to any local parameters defined by theGUI for presenting that data object type. Finally, the GUI may obtaindata values from the particular data object and render a visualrepresentation of the data values within a display device according tothe designated rules for that data object type.

Data may also be presented through various audio methods. In particular,data may be rendered into an audio format and presented as sound throughone or more speakers operably connected to a computing device.

Data may also be presented to a user through haptic methods. Forexample, haptic methods may include vibrations or other physical signalsgenerated by the computing system. For example, data may be presented toa user using a vibration generated by a handheld computer device with apredefined duration and intensity of the vibration to communicate thedata.

The above description of functions present a few examples of functionsperformed by the computing system of FIG. 7.1 and the computing nodesand/or client device in FIG. 7.2. Other functions may be performed usingone or more embodiments.

While one or more embodiments have been described with respect to alimited number of embodiments, those skilled in the art, having benefitof this disclosure, will appreciate that other embodiments may bedevised which do not depart from the scope as disclosed herein.Accordingly, the scope should be limited by the attached claims.

What is claimed is:
 1. A method comprising: determining, based on atiming measurement between a first digital radio communication device(DRCD) node and a second DRCD node, a distance between the first DRCDnode disposed on a tanker and the second DRCD node disposed about aloading arm or a hose end of a loading/unloading facility; andfacilitating, in response to determining the distance based on thetiming measurement, fluid payload loading/unloading of the tanker at theloading/unloading facility.
 2. The method of claim 1, wherein the firstDRCD node is disposed on the tanker to identify a position of at least acompartment coupler of the tanker; wherein the second DRCD node isdisposed about the loading arm or the hose end of the loading/unloadingfacility to identify the position of at least a loading/unloadingequipment of the loading/unloading facility.
 3. The method of claim 2,wherein facilitating loading/unloading of the tanker comprises:detecting, in response to measuring the distance, a mismatch between thetanker and the loading/unloading equipment; and preventing, in responseto detecting the mismatch, fluid payload loading/unloading of the tankerfrom the loading/unloading equipment.
 4. The method of claim 2, whereinfacilitating loading/unloading of the tanker comprises: detecting, inresponse to measuring the distance, a mismatch between the compartmentcoupler and the loading/unloading equipment; and preventing, in responseto detecting the mismatch, fluid payload loading/unloading of the tankervia the compartment coupler from the loading/unloading equipment.
 5. Themethod of claim 4, further comprising: presenting, in response todetecting the mismatch, a go/no go indication to an operator of thetanker or of the loading/unloading facility.
 6. The method of claim 1,wherein facilitating loading/unloading of the tanker comprises:wirelessly identifying the position of the tanker; and authenticating,based at least on the position of the tanker, the tanker for entry orexit from a secure area of the loading/unloading facility.
 7. The methodof claim 1, wherein facilitating loading/unloading of the tankercomprises: wirelessly identifying the position of the tanker; anddetermining, based at least on the position of the tanker, optimumqueuing of loading stations, unloading stations, and waiting areas ofthe loading/unloading facility.
 8. The method of claim 1, whereinfacilitating loading/unloading of the tanker comprises: wirelesslyidentifying the position of the tanker; and generating, based at leaston the position of the tanker, a collision warning.
 9. The method ofclaim 1, wherein facilitating loading/unloading of the tanker comprises:transferring tanker configuration information from the tanker to theloading/unloading facility, wherein the tanker configuration informationcomprises at least one selected from a group consisting of anidentification, a compartment count, a compartment capacity, acompartment coupler position relative to the first DRCD node.
 10. Themethod of claim 1, wherein facilitating loading/unloading of the tankercomprises: transferring tanker status to the loading/unloading facility,wherein the tanker status comprises at least one selected from a groupconsisting of a compartment fluid level, a compartment empty/fullstatus, last product loaded in each compartment, a tanker locationhistory, and a product drop log.
 11. The method of claim 1, whereinfacilitating loading/unloading of the tanker comprises: providing, usingthe first DRCD node, information storage on the tanker for use by aterminal automation system of the loading/unloading facility.
 12. Themethod of claim 11, wherein facilitating loading/unloading of the tankercomprises: transferring information from the terminal automation systemto a cab-mounted device of the tanker, wherein the information comprisesat least one selected from a group consisting of a Bill of Lading, aloaded product type in each compartment, delivery locations and routing,driver instructions, and business information relating to a transactionor vehicle load.
 13. The method of claim 1, wherein facilitatingloading/unloading of the tanker comprises: facilitating installation,configuration, and calibration of the first DRCD node or the second DRCDnode.
 14. The method of claim 1, wherein facilitating loading/unloadingof the tanker comprises: generating a map of the loading/unloadingfacility based at least on the distance between the first DRCD node andthe second DRCD node; and displaying the map on a cab-mounted device ofthe tanker or a terminal automation system of the loading/unloadingfacility.
 15. A computer program product comprising computer readableprogram code for: determining, based on a timing measurement between afirst digital radio communication device (DRCD) node and a second DRCDnode, a distance between the first DRCD node disposed on a tanker andthe second DRCD node disposed about a loading arm or a hose end of aloading/unloading facility; and facilitating, in response to determiningthe distance based on the timing measurement, fluid payloadloading/unloading of the tanker at the loading/unloading facility. 16.The computer program product of claim 15, wherein the first DRCD node isdisposed on the tanker to identify a position of at least a compartmentcoupler of the tanker; wherein the second DRCD node is disposed aboutthe loading arm or the hose end of the loading/unloading facility toidentify the position of at least a loading/unloading equipment of theloading/unloading facility.
 17. A distribution system comprising: one ormore computer processors; a terminal automation system comprisinginstructions, when executed, cause the one or more computer processorsto: determine, based on a timing measurement between a first digitalradio communication device (DRCD) node and a second DRCD node, adistance between the first DRCD node disposed on a tanker and the secondDRCD node disposed about a loading arm or a hose end of aloading/unloading facility; and facilitate, in response to determiningthe distance based on the timing measurement, fluid payloadloading/unloading of the tanker at the loading/unloading facility; afirst plurality of DRCD nodes, disposed on the tanker, comprising thefirst DRCD node; a second plurality of DRCD nodes, disposed about theloading/unloading facility, comprising the second DRCD node; the tankercomprising a compartment coupler, wherein the first DRCD node isdisposed on the tanker to identify a position of at least thecompaitment coupler; and the loading/unloading facility comprising aloading/unloading equipment, wherein the second DRCD node is disposedabout the loading arm or the hose end of the loading/unloading facilityto identify the position of at least the loading/unloading equipment.18. The distribution system of claim 17, wherein the tanker furthercomprises a first portion of the terminal automation system, and whereinthe loading/unloading facility further comprises a second portion of theterminal automation system.
 19. The distribution system of claim 17,wherein the instructions, when executed, further cause the one or morecomputer processors to: detect, in response to measuring the distance, amismatch between the tanker and the loading/unloading equipment; andprevent, in response to detecting the mismatch, fluid payloadloading/unloading of the tanker from the loading/unloading equipment.20. The distribution system of claim 17, wherein the instructions, whenexecuted, further cause the one or more computer processors to: detect,in response to measuring the distance, a mismatch between thecompailinent coupler and the loading/unloading equipment; and prevent,in response to detecting the mismatch, fluid payload loading/unloadingof the tanker via the compartment coupler from the loading/unloadingequipment.
 21. The distribution system of claim 17, wherein theinstructions, when executed, further cause the one or more computerprocessors to present, in response to detecting the mismatch, a go/no goindication to an operator of the tanker.
 22. The distribution system ofclaim 17, wherein the instructions, when executed, further cause the oneor more computer processors to: wirelessly identify the position of thetanker; and authenticate, based at least on the position of the tanker,the tanker for entry or exit from a secure area of the loading/unloadingfacility.
 23. The distribution system of claim 17, wherein theinstructions, when executed, further cause the one or more computerprocessors to: wirelessly identify the position of the tanker; anddetermine, based at least on the position of the tanker, optimum queuingof loading stations, unloading stations, and waiting areas of theloading/unloading facility.
 24. The distribution system of claim 17,wherein the instructions, when executed, further cause the one or morecomputer processors to: wirelessly identify the position of the tanker;and generate, based at least on the position of the tanker, a collisionwarning.
 25. The distribution system of claim 17, wherein theinstructions, when executed, further cause the one or more computerprocessors to: transfer tanker configuration information from the tankerto the loading/unloading facility, wherein the tanker configurationinformation comprises at least one selected from a group consisting ofan identification, a compathnent count, a compathnent capacity, acompartment coupler position relative to the first DRCD node.
 26. Thedistribution system of claim 17, wherein the instructions, whenexecuted, further cause the one or more computer processors to: transfertanker status to the loading/unloading facility, wherein the tankerstatus comprises at least one selected from a group consisting of acompailinent fluid level, a compartment empty/full status, last productloaded in each compaitment, a tanker location history, and a productdrop log.
 27. The distribution system of claim 17, wherein the firstDRCD node comprises information storage on the tanker for use by thefirst portion and the second portion of the terminal automation systemto exchange information.
 28. The distribution system of claim 17,wherein the tanker further comprises a cab-mounted device, wherein theinstructions, when executed, further cause the one or more computerprocessors to transfer information to the cab-mounted device, andwherein the information comprises at least one selected from a groupconsisting of a Bill of Lading, a loaded product type in eachcompaitinent, delivery locations and routing, driver instructions, andbusiness information relating to a transaction or vehicle load.
 29. Thedistribution system of claim 17, wherein the instructions, whenexecuted, further cause the one or more computer processors to:facilitate installation, configuration, and calibration of the firstDRCD node or the second DRCD node.
 30. The distribution system of claim18, wherein the instructions, when executed, further cause the one ormore computer processors to: generate a map of the loading/unloadingfacility based at least on the distance between the first DRCD node andthe second DRCD node.
 31. The distribution system of claim 17, furthercomprising one or more service station drops, and wherein a transfer ofmaterial from the tanker to the one or more service station drops istracked.
 32. The distribution system of claim 31, wherein the transferof material from the tanker to the service station drops is tracked viabarcode, RFID tags, ultra-wideband trackers, or GPS trackers.